I agree that redux was a solution built to solve react issues but conceptually it's just a state management tool which I think can apply to some angular applications. I haven't worked extensively with different angular redux flavors but I have worked a lot with ngrx. I completely agree that it adds an enormous amount of boilerplate code but in certain circumstances that boilerplate becomes a powerful framework of state management. In most applications state can and should be managed in services and alternative persistent storage etc. However in complex applications that rely on pulling from large data sources in real-time and share that data across the application I'd argue that a redux style store is incredibly beneficial. At some point with large applications, storing your state in services just becomes you rewriting the existing functionality of a redux style library. I get that dispatching actions for every little thing can become tedious but I think if you build your store thoughtfully it will benefit you in the end.

Jake Leveroni

Alexander Joseph

A look at the rise of Redux and misconceptions surrounding its need in the Angular world.

Stephen E.

Why you should NEVER use Redux with Angular

Stephen E.

Why you should NEVER use Redux with Angular

Trending